chore: change controller's deploy strategy to RollingUpdate due to leader election #3334
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist:
"fix(controller): Updates such and such. Fixes #1234"
.background
Though there was a constraint to use deployment strategy
Recreate
due to race condition #38, now it seems we don't have to care about deployment strategy as below.https://cloud-native.slack.com/archives/C01U781DW2E/p1640199673233000
argo-helm got the PR that let controller's deployment strategy configurable, so I wonder we can change the default strategy as
RollingUpdate
. 🙋